System for transferring multimedia information

ABSTRACT

A multimedia information transfer system includes a multimedia server and a client server system coupled with the multimedia server through a communication network and transfers data transmitted from the multimedia server to a server of the client server system. The multimedia server stores data streams of the multimedia information and reproduces the information. The client requests the multimedia server to transfer data, stores the transferred data block and displays the stored data block concurrently with the storage of the next coming data block.

BACKGROUND OF THE INVENTION

The present invention relates to a system for transferring multimediainformation. Multimedia information is a generic term for several kindsof digital information coexisting in one information media, thosedigital information including digital moving pictures, digital stillpictures, digital text data, and digital audio data. More particularly,the present invention relates to the multimedia information transfersystem which is suitable to transferring data from a multimedia serverfor generating large amounts of multimedia information having streamswith high bit rates to a server and a client coupled in a client serversystem (termed CSS) through a multimedia information network representedas a CATV network or an internet.

In general, the CSS used for business is arranged so that part of workto be processed by a server of the CSS is given to a multimedia serversuch as an outsourcing center and the processed result is given back tothe CSS through a network.

The multimedia server, to which part or all of the functions about aproject are entrusted, a setup including, and a promotion of aninformation processing system used for business in an enterprise isrequired to process a large amount of data streams with high bit ratesin order to make good use of the multimedia information for backing upthe processing of the CSS. Hence, the multimedia server is generallyarranged by the leased hardware, a supercomputer (super parallelmachine), a mainframe, a general-purpose server machine, a configurationof standard computers interconnected with one another (distributedarchitecture), or the like.

This kind of technology is described in “Technical Trend Toward VideoServer Served as Core of VOD” of “Business Communication” November 1994,issued by Business Communication, Ltd., for example.

When transferring data between different kinds of information processingsystems coupled through a communication network, an extended waitingtime for access to the communication network is a significant problem.In particular, when transferring a large amount of data such asmultimedia information, the waiting time for access and the transfertime are bottlenecks with regards to efficiency of the transfer system.

The technology described in the aforementioned publication hasdifficulty in overcoming the bottleneck in connection with the networkand in quickly and efficiently transferring data between the multimediaserver and a plurality of CSS servers and between the CSS server and aplurality of clients. These difficulties makes it impossible for aclient for using the data transferred thereto to sufficiently meet therequirements of receiving a large amount of data streams with high bitrates in real time and performing reproducing processes of themultimedia information represented as image data, those reproducingprocesses including a fast feed, a stop, and a reverse like reproductionof a video disk, for example.

SUMMARY OF THE INVENTION

It is an object of the present invention to provide a system fortransferring multimedia information in a system including a multimediaserver, CSS servers, and clients, the system being arranged to simplifytransmitting processes between the multimedia server and the CSS serverand receiving processes between the CSS server and to the client andsolve a bottleneck in connection with a network between the CSS serverand a plurality of clients for the purpose of keeping the data transferquick and efficient.

According to the present invention, a multimedia information transfersystem includes a multimedia server and a client server system coupledwith the multimedia server through a network so that the multimediaserver transfers data to a server and clients of the client serversystem, the multimedia server having means for storing and reproducingdata streams of the multimedia information, the client having means forrequesting the multimedia server to output data and storing thetransferred data and means for displaying the data concurrently whenstoring the data.

According to an aspect of the present invention, the multimedia serveroperates to divide the multimedia information into N data blocks (N isan integer of 2 or more), each of which contains n data units (n is aninteger of 1 or more), and sequentially transfer the data units to theserver of the client server system on the data blocks. Then, the clientserver system operates to transmit the data block containing n dataunits to the client for requesting the server to output the data.

Further, according to another aspect of the present invention, eachnetwork node of the multimedia server and the server and the clients ofthe client server system has network addresses dedicated the receipt andtransmission of data. The multimedia server and the server of the clientserver system, which transmit the multimedia information, have their ownmatrix tables each for managing a receiving status and a process requeststatus on the receiving side and operate to set the request from thereceiving side to a field of the matrix and transfer the data based onthe status.

According to another aspect of the present invention, the clientrequesting the process receives data at the address defined on thereceiving side the multimedia information, which is processed by themultimedia server, the data being divided into N data blocks andtransferred in groups of n data units in each data block, and a group ofn data units being sent to the defined address. Further, the clientprovides a function of displaying the streams of the multimediainformation concurrently while storing the streams of data. The clientenables concurrent storage and display of the data streams so that theclient, by itself, can control a fast feed, a stop, a reverse, and aplay in real time.

The multimedia server has a matrix table for managing a processrequesting status from the side for requesting the process and a receivestatus for the processed result data for each service. When the side forrequesting the process operates to set the process requesting status andthe receive status to the matrix table of the multimedia server, thematrix table reads these statuses in sequence and sets the statuses tothe proper fields for the matrix table. Hence, the multimedia server forproviding the service is capable of transmitting the processed resultdata for the services of the CSS server and the clients as viewing thestatus of the matrix table independently of the update of the matrixtable.

Further, according to another aspect of the present invention, asmentioned above, the data transfer is executed between the CSS serverand the client. Further, the status management of the matrix table andthe transmission of the processed result data are allowed to be executedby the device for providing the multimedia server and the CSS serverwith the services. Hence, the multimedia server, the CSS server, and theclient are capable of doing their performing processes independently ofone another and the two former servers can meet the request from theclient and transfer the processed result data.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other objects, features, and advantages of the presentinvention will become more apparent upon a reading of the followingdetailed description and drawings, in which:

FIG. 1 is a block diagram showing an arrangement of a system fortransferring multimedia information according to an embodiment of thepresent invention;

FIG. 2 is a view showing a format of a received data status for aclient;

FIG. 3 is a view showing a format of a received data set for a client;

FIG. 4 is a view showing a format of a table for each type of processrequests for a CSS server;

FIG. 5 is a view showing a format of a matrix table for managing aclient status for a CSS server;

FIG. 6 is a view showing a format of a received data status for a CSSserver;

FIG. 7 is a view showing a format of a transmission and receive data setfor a CSS server;

FIG. 8 is a view showing a format of a transmission data set for amultimedia server;

FIG. 9 is a view showing a format of a matrix table for managing a CSSstatus for a multimedia server;

FIG. 10 is a view showing a list of objects to be served for a CSSserver;

FIG. 11 is a view showing a format of objects to be served for amultimedia server;

FIG. 12 is a flowchart (part 1) showing a processing operation of asystem for transferring multimedia information according to anembodiment of the present invention; and

FIG. 13 is a flowchart (part 2) to be combined with the flowchart ofFIG. 12, showing a processing operation of a system for transferringmultimedia information according to an embodiment of the presentinvention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Hereafter, the description will be oriented to a system for transferringmultimedia information according to an embodiment of the presentinvention.

In FIG. 1, a numeral 1 denotes a matrix table for managing a CSS status.A numeral 2 denotes a multimedia server. A numeral 3 denotes a disk unitfor storing a data set to be transmitted. Numerals 4, 9, 18, 23, 26 29and 32 denote LAN adapters provided with network addresses dedicated fortransmission. Numerals 5, 8, 17, 22, 25, 28 and 31 denote LAN adaptersprovided with network addresses dedicated for receive. A numeral 6denotes a communication network, specifically, a wide area network (WAN)which is larger in scale than the LAN. Numerals 7, 36, and 37 denoteinterface devices coupled through the LAN. Numerals 10 and 24 denote CSSservers. A numeral 11 denotes a harddisk where a data set to be receivedor transmitted is registered. Numerals 12, 16 and 21 denote statuses forreceived data. A numeral 13 denotes a matrix table for managing a clientstatus. Numerals 14, 19, 27 and 30 denote clients. Numerals 15 and 20denote harddisks a received data set is registered. A numeral 38 denotesa display unit coupled to each client.

Moreover, the network addresses dedicated for transmission of the LANadaptors 4, 9, 18, 23, 26, 29 and 32 may be made to be identical withthe network addresses dedicated for receive of the LAN adaptors 5, 8,17, 22, 25, 28 and 31. That is, one LAN adaptor having a single networkaddress may have both of the transmitting and receiving functions.

The system according to an embodiment of the invention, as shown in FIG.1, includes devices on the multimedia server side for backing up the CSSand a plurality of devices on the CSS side coupled through the network 6such as the WAN and LAN devices 37, 7 and 36.

The devices on the multimedia server side includes the multimedia server2 for backing up the CSS, the matrix table 1 for managing the statusesof the processes requested by the CSS side coupled to this server 2 andof the processed result data, a disk device 3 for storing a data set ofthe processed result to be transmitted to the CSS side, a service list34 where the CSS's to be served are registered at network addressesdedicated for the outputs, and the LAN adaptors 4 and 5 coupled to theLAN device 37.

One of the devices on the CSS side is arranged to have the CSS server 10and the clients 14 and 19 coupled through the LAN adaptors 8, 9, 17, 18,22, and 23 and the LAN device 7. The CSS server 10 is coupled to thedisk device 11 for storing a data set of the processed result receivedfrom the multimedia server 2 and another data set to be transmitted tothe client, a received data status 12, a table for each type ofprocessed request, and the service list 33. The clients 14 and 19 arecoupled to the disk devices 15 and 20, respectively, for storing thedata sets of the processed result received from the multimedia server 2and the received data statuses 16 and 21. The CSS server 24 and theclients 27 and 30 on the CSS side have the same arrangement as theforegoing devices on the CSS side.

In turn, the description will be oriented to the formats of the tables,the lists, the statuses and the like coupled to the foregoing multimediaserver 2, the CSS server 10, and the clients 14 and 19, respectively,with reference to the appended drawings.

The received data statuses 16 and 21 coupled to the clients 14 and 19are referenced and updated when the client requests the CSS server toperform a process and receive the data blocks of the processed result.As shown in FIG. 2, the status 16 or 21 is composed of network addresses40 to 43 dedicated for input and output of the CSS server and thesubject client, a process request date 44, a process request time 45, aprocess request ID 46, a status update flag 47, and receive flags 48 to50 for the first to the N-th data blocks (N is an integer of 2 or more).

The network addresses 40 to 43 may use a single common network addressfor transmission and receipt of data in place of the network addressesdedicated for transmission and receive.

The received data set registered in the harddisk 15 or 20 has a formatincluding header information 51 and the first to the N-th data blocks 52to 54 as shown in FIG. 3. The header information 51 includes of networkaddresses 55 to 58 dedicated for inputs and outputs of the CSS serverand the subject client, the process request date 59, the process requesttime 60, and the process request ID 61, which format is the same as thatdescribed with reference to FIG. 2.

Each data block includes n (n is an integer of 1 or more) data units 200and a header 201 at the head of the data. The header 201 contains a datablock number and a data unit number stored as address information.

The table for each type of process request 35 coupled to the CSS server10, as shown in FIG. 4, enables the storage of m (m is an integer of 1or more) pieces of information 62 to 65 for each type of processrequest. Each piece of information for each type of process requestincludes a process request ID 66 of a client, a backup processing flag67, and a maximum value of a service time of the CSS server.

The matrix table 13 for managing a client status coupled with the CSSserver 10, as shown in FIG. 5, enables the storage of m pieces of statusinformation 69 to 72 for the process requests given by the clients. Eachstatus information includes network addresses 73 to 76 dedicated forinputs and outputs of the CSS server and the clients, which are similarto the network addresses described with reference to FIG. 2, a processrequest date 77, a process request time 78, a process request ID 79, andreceive flags 81 to 83 for the first to the N-th data blocks. Thedifferent aspect of FIG. 5 from FIG. 2 is the provision of a transfercompletion flag 80 in place of a status update flag.

The received data status 12 coupled to the CSS server 10, as shown inFIG. 6, is composed of network addresses 84 to 89 dedicated for inputsand outputs of the multimedia server, the CSS server, and the clients, aprocess request date 90, a process request time 91, a process request ID92, a status update flag 92, and receive flags 94 to 96 for the first tothe N-th data blocks.

The data set for transmission and reception of data, registered in thedisk device 11 coupled to the CSS server 10, has such a format as shownin FIG. 7. The format is includes a header information 97 and the firstto the N-th data blocks 98 to 100. The header information 97 includesnetwork addresses 101 to 106 dedicated for inputs and outputs of themultimedia server, the CSS server, and the clients, which are the samenetwork addresses as those described with reference to FIG. 6, a processrequest date 107, a process request time 108, and a process request ID109.

The service list 33 coupled to the CSS server 10, as shown in FIG. 10,enables the storage of (n is an integer number.) network addresses 180to 183 dedicated for outputs of the clients served by the subject CSSserver 10.

The data set for transmission included in the disk device 3, whichstores the data set of the processed result to be transmitted to the CSSside coupled to the multimedia server 2, has such a format as shown inFIG. 8. The format includes header information 110 and the first to theN-th data blocks 111 to 113. The header information 110 is the same asthat described with reference to FIG. 7. That is, the header information110 includes network addresses 114 to 119 dedicated for inputs andoutputs of the multimedia server, the CSS server and the clients, aprocess request date 120, a process request time 121, and a processrequest ID 122.

Each data block includes n (n is an integer of 1 or more) data units300. Further, a header 301 is included at the head of the data. Theheader 301 saves a data block number and a data unit number as addressinformation.

The matrix table 1 for managing the CSS status, which table is coupledto the multimedia server 2, enables the storage of m pieces of statusinformation 123 to 126 for the process requests given by the CSS serversas shown in FIG. 9. Each status information has similar composition tothat described with reference to FIG. 5. That is, each statusinformation includes network addresses 127 to 132 dedicated for inputsand outputs of the CSS servers, the clients and the multimedia server, aprocess request date 133, a process request time 134, a process requestID 135, a transfer completion flag 136, and receive flags 137 to 139.

The service list coupled to the CSS server side, as shown in FIG. 10,enables the storage of n network addresses 180 to 183 dedicated foroutputs of the clients served by the subject CSS server.

The service list 34 coupled to the multimedia server 2, as shown in FIG.11, enables the storage of n network addresses 184 to 187 dedicated foroutputs of the CSS servers served by the subject multimedia server 2.

As set forth above, according to an embodiment of the invention, thesystem configured of the multimedia server, the CSS server and theclients is arranged to simplify a transmitting process between themultimedia server and the CSS server and the receiving process betweenthe CSS server and the clients and solve the bottleneck in networkingbetween the multimedia server and CSS servers and between the CSS serverand the clients for the purpose of quickly and efficiently transferringthe data.

In turn, the description will be oriented to the operation oftransferring the multimedia information in the system according to theforegoing embodiment of the invention with reference to FIGS. 12 and 13.In this embodiment of the invention, the clients, the CSS server and themultimedia server are operated independently of one another. Further,the multimedia server operates to back up the process executed by theCSS server. In response to the request given from the CSS server, themultimedia server operates to transfer the multimedia informationgenerated by the multimedia server itself to the CSS server. Further,the CSS server operates to transfer the received multimedia informationto the client for requesting the multimedia information.

At first, the processing on the client side will be described.

(1) Now, assume that a process request is issued for transferring themultimedia information to the multimedia server 2. In response to therequest, the client 14 operates to set a process request status to thereceived data 16 and waits for the processed result data transferredfrom the CSS server 10 (steps 140 and 141).

(2) As will be described below, the CSS server 10 performs the processrequested by the client 14 or entrusts the process to the multimediaserver 2. After obtaining the data of the processed result, the CSSserver 10 or the multimedia server 2 operates to transfer the data tothe client 14. The data of the processed result is divided into N datablocks, and each group of n data units of each data block is transferredback to the client 14 in sequence. The client 14 receives the processedresult at each group of n data units (step 142).

(3) The process is executed for registering the processed result datareceived from the CSS server 10 in the harddisk 15 for storing the dataset for receive (step 143). The received data status 16 is updatedaccording to the receive status of the processed result data of theclient 14 (step 144). Specifically, the data block receive flags for thestatuses 48, 49, 50 and the like as shown in FIG. 2 are set, and thestatus update flag 47 is set as well.

When all n data units contained in one data block are received, inresponse to the display request from the display unit 38, n pieces ofdata units are displayed on the screen (steps 146 and 147). When theimage information is displayed, as in the playback of a video disk, forexample, the image section at any position is selectively displayed byspecifying an address. Further, the still playback, the fast forwardingor the reversing are also made possible.

(4) It is checked if all N data blocks are received. If it is notcompleted, the process from the step 142 is repeated (step 145).

(5) In the check at the step 145, if the receipt of all N data blocks iscompleted, the process is terminated.

In addition, the client 14 enables to display the received dataconcurrently with the receipt of each group of n data units.

Next, the description will be oriented to the process executed by theCSS server.

(6) The CSS server 10 operates to sequentially read the received datastatuses 16 and 21 of the client where the client itself sets theprocess request at the step 141 as referring to the service list 33(step 148).

(7) After reading the received data status 16 set by the client 14 forthe purpose of the process request at the step 141, the CSS server 10operates to add the network address 40 dedicated for an input of the CSSserver, the network address 41 dedicated for an output of the CSSserver, the network address 42 dedicated for an input of the client, thenetwork address 43 dedicated for an output of the client, the processrequest date 44, the process request time 45, and the process request ID46, all of which are shown in FIG. 2, to the matrix table 13 formanaging the client status as the data items 73 to 79 shown in FIG. 5.If the received data status 16 has no content, the record of the fact isadded to the matrix table 13 (step 149).

(8) By reading the table 35 for each type of process request, it ischecked if the request for the process is to be backed up by themultimedia server (steps 150 and 151).

(9) If it is determined that the request for the process is not to bebacked up at the step 151, the process request is determined to beexecuted by the subject CSS server. In response to the process requestfrom the client 14, the CSS server operates to perform the requestedprocess (step 152).

(10) It is determined if the process at the step 152 is terminatedwithin a MAX value 68 of the service time of the CSS server in therecord set to the table 35 for each type of process request shown inFIG. 6 (step 153).

(11) If in the determination at the step 153 the process at the step 152is terminated within the MAX value of the service time, the multimediainformation created at the step 152 is divided into N data blocks andthen are registered as the data set for transmission and receive in thedisk 11 (step 154).

(12) If in the determination at the step 151 the process request ID 79of the record added to the matrix table 13 for managing the clientstatus at the step 149 is the same as the process request ID 66contained in the process request table 35, the flag 67 for backing upthe record is set, and the process request is determined to be theback-up request, or if in the determination at the step 153, the processat the step 152 is determined not to be terminated within the MAX valueof the service time, the CSS server operates to set the process requestread from the client to the received data status 12 shown in FIG. 6 andwaits for the processed result data transferred from the multimediaserver 2 (step 158).

(13) As will be described below, the multimedia server 2 performs theprocess requested by the CSS server 10 and, if the processed result datais obtained, transfers the data to the CSS server 10. The processedresult data is divided into N data blocks, and each group of n dataunits contained in each data block is transferred to the CSS server onegroup by one group. The CSS server 10 receives the processed result ateach group of n data units (step 159).

(14) The CSS 10 server performs a process for registering the processedresult data received from the multimedia server 2 in the harddisk 11 forstoring the data set for transmission and receive (step 160). Then, theCSS server 10 updates the received data status 12 according to theprocessed result data received status of the CSS server 10 itself (step161). Specifically, the data block receive flags for the statuses 94,96, 96 and the like shown in FIG. 6 are set and the status update flag93 is set as well.

If all n data units are received in one data block at a step 161, theoperation goes to a step 155, at which the content of the matrix tablefor managing the client status shown in FIG. 5 is read.

(15) It is checked that the receipt of all N data blocks is completed.If not completed, the process from the step 159 is repeated (step 162).If all N data blocks are received, the process is terminated.

(16) At a step 154 (see FIG. 12), the data of the processed result givenby the subject CSS server 10 is registered in the harddisk 11 forstoring the data set for transmitting and receiving. On the terminationof the process, the matrix table 13 for managing the client status shownin FIG. 5 is read in sequence (step 155).

(17) If a transfer completion flag 80 in the matrix table 13 formanaging the client status is set and all the receive flags from thefirst to the N-th data block receive flags 81 to 83 are set, thecorresponding records are deleted from the matrix table 13 for managingthe client status, and the process is terminated (steps 156 and 157).

(18) If it is determined that the transfer completion flag 80 is off byreferring to the matrix table 13 for managing the client status, theprocess for transmitting standby data blocks at each group of n dataunits is executed by repeating the process from the step 155. On thetermination of transferring all N data blocks, the transfer completionflag 80 is set (step 163).

(19) The received data statuses 16 and 21 updated by the client 14 atthe step 144 are read in sequence (step 164).

(20) The content of the received data status 16 is checked. If thestatus update flag 47 is set, the matrix table 13 for managing theclient status is updated and if the transfer of the N data blocks isterminated, the transfer completion flag 80 is set. If the flag 47 hasbeen already off, nothing is executed (step 165).

Of the foregoing processes of the CSS server, the processes at the steps155 to 157 and 163 are executed in parallel to and independently of theprocesses at the steps 164 and 165.

In turn, the description will be oriented to the process of themultimedia server.

(21) The multimedia server 2 operates to sequentially read the receiveddata status 12 of the CSS server where the process request is set by theCSS server itself at the step 158 by referring to the service list 34(step 166).

(22) The multimedia server 2 operates to read the received data status12 of the client set by the CSS server 10 for the process request at thestep 158 and to add a record composed of the network address 127dedicated for an input of the multimedia server, the network addressdedicated for an output of the multimedia server, the network address129 dedicated for an input of the CSS server, the network address 130dedicated for an output of the CSS server, the network address 131dedicated for an input of the client, the network address 132 dedicatedfor an output of the client, the process request date 133, the processrequest time 134, the process request ID (Identification Information)135 to the matrix table 1 for managing the CSS status shown in FIG. 9.If the received data status 12 has no content, the record of the fact isadded. Then, the update flag 93 is off (step 167).

(23) In response to the process request issued by the CSS server 10, themultimedia server performs a backup operation, divides the createdmultimedia information into N data blocks, and registered them as a dataset for transmission in the disk 3 (steps 168 and 169).

(24) The multimedia server operates to sequentially read the matrixtable 1 for managing the CSS status shown in FIG. 9 updated at the step167 (step 170).

(25) If the transfer completion flag 136 included in the matrix table 1for managing the CSS status is set and all receive flags from the firstto the N-th data block receive flags 137 to 139 are set, thecorresponding records are deleted from the matrix table 1, and then theprocess is terminated (steps 171 and 175).

(26) If it is determined that the transfer completion flag 136 is off byreferring to the matrix table 1, the process for transmitting thestandby data blocks to the corresponding CSS sever 10 at each group of ndata units is executed by repeating the process from the step 170. Onthe termination of all N data blocks, the transfer completion flag 136is set (step 172).

(27) The multimedia server operates to sequentially read the receiveddata status 12 of the CSS server which is updated by the CSS server 10at the step 161 (step 173).

(28) The content of the received data status 12 is checked. If thestatus update flag 93 is set, the multimedia server updates the matrixtable 1 for managing the CSS status. If the transfer of all N datablocks is completed, the transfer completion flag 136 is off. If theflag 136 has been already off, nothing is executed (step 174).

Of the foregoing processes of the multimedia server, the processes atthe steps 170 to 172 are executed in parallel to and independently ofthe processes at the steps 173 and 174.

In the foregoing embodiment of the invention, the client for issuing theprocess request is just required to receive the multimedia informationfrom the multimedia server at the address defined on the receives sideand set each group of n data units to the address. As mentioned above,the multimedia information is the result processed by the multimediaserver. The multimedia information is divided into N data blocks and istransferred at each group of n data units of each data block. Further,the streams of the multimedia information are allowed to be displayedconcurrently when those streams are stored. The storage of streams ofmultimedia data at each group of n data units being received is executedin parallel with and concurrently with the display of one previousreceived group of n data units. Like the playback of the video disk, theclient thus provides a capability of controlling a fast feed, a stop, areverse, a playback of the multimedia information in real time.

The multimedia server includes a matrix table for managing the processrequest status and the processed result data received status from theside for requesting the process at each service. When the requestingside sets the process request status and the processed result datareceived status from the requesting side, the multimedia server operatesto sequentially read these statuses and set the statuses to thecorresponding fields of the matrix table. The multimedia server that isa provider of the service enables the transmission of the processedresult data to the service such as the CSS server or the client asviewing the status of the managing matrix table independently of theupdate of the matrix table.

Further, according to the embodiment of the invention, the data transferbetween the CSS server and the client is made possible like theforegoing operation. The multimedia server, the CSS server, and theclient are executing their processes independently of one another whilethe process request and the processed result data are transferred amongthe CSS server, the multimedia server, and the client.

As set forth above, according to the present invention, the data of theresult processed by the multimedia server is divided into N data blocksand each group of n data units of each data block is transferred to theaddress defined by the receiving side. The multimedia server, the CSSserver, and the client are thus capable of executing their processesindependently of one another. Hence, the multimedia server, the CSSserver, and the client are reduced in scale as securing a response tothe request from the client.

In case the multimedia server is coupled to two or more CSS servers orthe CSS server is coupled to two or more clients, the system accordingto the invention can solve the bottleneck in networking between themultimedia server and the CSS servers and between the CSS server and theclients. Further, according to the present invention, only the side fortransmitting the processed result data, such as the multimedia server orthe CSS server, operates to transmit the data. Hence, the CSSarrangement may be dynamically changed. Besides, even in this case, thepresent invention offers an effect that the client side does not needany modification.

While the present invention has been described above in conjunction withpreferred embodiments, one of ordinary skill in the art would be enabledby this disclosure to make various modifications to these embodimentsand still be within the scope and spirit of the invention as defined inthe appended claims.

What is claimed is:
 1. A multimedia information transfer systemcomprising: a multimedia server; a client server system coupled to saidmultimedia server via a network, for transferring multimedia informationfrom said multimedia server to a client server and one or more clientsincluded in said client server system, a matrix table coupled to saidmultimedia server, for managing a receive status and a process requeststatus of said client server system; wherein said multimedia server,said client server and said one or more clients correspond to differentnodes in said network having network addresses dedicated forcommunication; wherein said multimedia server comprises: means forstoring and reproducing data streams of multimedia information; andmeans for dividing said multimedia information into N (N being aninteger of 2 or more) data blocks, each of which includes n (n being aninteger of 1 or more) data units, for sequentially transferring saidmultimedia information divided into N data blocks to said client serverof said client server system on a data basis, and for sending a requestto transfer said multimedia information divided into N data blocks fromsaid client server system to a proper field of said matrix table;wherein said client server comprises: means for requesting saidmultimedia server to divide said multimedia information into said N datablocks and to transfer data blocks of said multimedia information tosaid client server, and for storing and registering the transferred datablocks of said multimedia information; and means for displaying saidmultimedia information concurrently with the storage and registration ofsaid multimedia information.
 2. A system as claimed in claim 1, whereinsaid matrix table includes a transfer status area which indicateswhether the transfer of all N data blocks of said multimedia informationis complete, and a receive status area which indicates the reception ofsaid multimedia information, wherein said transfer and receive statusareas are updated each time transfer and reception operations areexecuted.
 3. A system as claimed in claim 1, wherein said multimediainformation divided into N data blocks is transferred from saidmultimedia server to said client server of said client server systemindependently of the update of said transfer and receive status areas ofsaid matrix table.
 4. A system as claimed in claim 1, wherein saidmultimedia information divided into N data blocks is transferred fromsaid client server of said client server system to said clientindependently of the update of said transfer an receive status areas ofsaid matrix table.
 5. A system as claimed in claim 1, wherein, in saidmultimedia information divided into N data blocks, each of said datablocks includes an address for identifying a subject data block, andeach of n data units included in each data block includes a dataaddress.
 6. A system as claimed in claim 5, wherein said multimediainformation includes image information, and when said image informationis transferred from said multimedia server to said client, said clientoperates to specify the address for identifying said data blocks of saidimage information stored and the data address of a specific one of saiddata units for reproducing said image information.
 7. A system asclaimed in claim 1, wherein said network addresses dedicated forcommunications includes one network address dedicated for receiving saidmultimedia information, and another network address dedicated fortransmitting said multimedia information.
 8. A multimedia server fortransferring multimedia information to a client server system through acommunication network in response to a transfer request for saidmultimedia information from said client server system, comprising: meansfor dividing said multimedia information into N (N being an integer of 2or more) data blocks, each data block containing n (n being an integerof 1 or more) data units, in response to a request by said client serversystem that said multimedia server transfer said multimedia informationdivided into N data blocks, each block containing n data units, to saidclient server system; means for transferring the requested data blocksof said multimedia information to said client server system on a datablock basis; and a table having a transfer status area which indicatesif a transfer operation of all N data blocks of said multimediainformation is complete and a receive status area which indicates if areceive operation of all N data blocks of said multimedia informationtransferred from said client server system is complete, the transferoperation of said multimedia information divided into N data blocksbeing executed based on said status information of said table.
 9. Aclient server system containing a client server and a plurality ofclients coupled to said client server and for receiving multimediainformation from a multimedia server through a communication network,comprising: means for receiving requests from respective ones of saidclients for transfer thereto of multimedia information divided into N (Nbeing an integer of 2 or more) data blocks; means for receiving saidmultimedia information divided into N data blocks in a format of datablock units, and for storing and registering said data blocks in dataset areas corresponding respectively to said clients; and display meansfor reproducing and displaying said multimedia information of saidstored data block while a next data block of said multimedia informationis being received.
 10. A storage medium for storing a program codeexecutable by a computer, comprising: a first section which stores aprogram code to divide multimedia information into N (N being an integerof 2 or more) data blocks, each data block including n (n being aninteger of 1 or more) data units in response to a transfer request formultimedia information divided into N data blocks, each block containingn data units, from said client server system; a second section whichstores a program code to transfer said data blocks of said multimediainformation to said client server system in data block units based onstatus information stored in a table; and a third section which stores aprogram code to generate transfer status information indicating if atransfer operation of all N data blocks of said multimedia informationis complete, receives receipt and storage status information indicatingif a receive and storage operation of said N data blocks of saidmultimedia information transmitted from said client server system iscomplete, and stores said transfer and receive status information in atable.
 11. A storage medium for storing a program code executable by acomputer, comprising: a first section which stores a program code toreceive and register requested multimedia information divided into Ndata blocks, each data block containing n data units, transmitted from amultimedia server in data block units and stores said data blocks; asecond section which stores a program code to reproduce and display saidmultimedia information including said stored data block while a nextdata block of said multimedia information is being received; and a thirdsection which stores a program code to generate receive statusinformation indicating if a receive operation of said data blocks iscomplete and to transmit said receive status information to saidmultimedia server.